home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
gt_power
/
bgpck12.zip
/
BGPCK.DOC
< prev
next >
Wrap
Text File
|
1990-06-27
|
10KB
|
211 lines
VOICE B.J. GUILLOT MODEM
(713) 893-9123 2611 RUSHWOOD CIRCLE (713) 893-9124
HOUSTON, TX 77067-1941
Copyright B.J. Guillot (C) 1990 - All Rights Reserved
=============================================================
BGPCK 1.2 26 JUN 90
=============================================================
-------------------------------------------------------------
ABSTRACT
-------------------------------------------------------------
BGPCK uses the users last read pointers from the areas they
are joined into and generates a zip file that contains any
new messages. It is similar to the OZ FASTMAIL program, but
gives the users the ability to reply to messages when using
BGRDR or a compatible reader program.
It gives users the ability to read messages on their own time
freeing up time on your board as well as letting them have
the change to use their favorite text editor as well. BGPCK
works with both GT 14 and 15 series and with both versions of
GT, it gives the users full features of GT 15, including the
ability to quote and unjoin areas at will.
-------------------------------------------------------------
EXECUTION AND COMMAND PARAMETERS
-------------------------------------------------------------
BGPCK now requires a configuration file. Example fields:
tranquil board id, 8 characters max
c:\gt\bgpck work directory
c:\util path where pkzip/pkunzip are located
B.J._Guillot sysop name - underscored - correct case
150 maximum messages packed per area
1024 minimum disk k required to run
c:\util\dwredir.com pathname of dwredir; only necessary if
you are using doorway 2.06+
For BGPCK to run, the configuration file must be located in
the GTPATH directory.
The space bar character is treated as a comment character.
The board ID must be no longer than eight characters. It is
used as the filename of the files created with BGPCK. You
should try to make your board ID unique to your area; i.e.,
two boards both using the name of "ULTIMATE" in the same
area code could be dreadful for users if they wish to use
BGPCK on both of those boards.
If you wish to run BGPCK on GT 13/14 systems, just must put a
dollar sign in front of the board identifaction line. Ex:
TRANQUIL use the door with GT 15 systems
$TRANQUIL use the door with GT 13/14 systems
The sysop name should have an underscore replacing any
spaces in the sysop name or BGPCK will think the sysop's
last name is a comment.
The maximum messages per conference give the sysop some
control of what is going on. I recommend you use a number
no greater than 100. The space the messages take add up
very quickly. (One message takes a minmim of 256 bytes).
If more than 100 messages are in a base, BGPCK will pull
out the first 100, not the last 100. The user can call
back and get the other messages left over later rather than
having to reset the pointers manually. This may change.
The minimum disk space required also gives you some control.
The number must be in kilobytes; i.e., 1024 would be one
megabyte. I would recommend that you at least have one
megabyte to do work with. If you with anything lower, you
risk the possibility of a crash from low disk space. The
user will be notified if disk space is too low on the host
system.
The last two fields are new. The upload and download
directories are provided so that the sysop can use BGRDR
without having to move files around.
Syntax: BGPCK comport [/D /E /G /M]
BGPCK uses one command line parameter. The com port that
will be used. You can use...
BGPCK %2
...to care of everything for you assing GATEWAY was activated
before hand.
The /D parameter informs BGPCK to use DOORWAY and the DWREDIR
program.
The /E parameter informs BGPCK to use DSZ.EXE.
The /G parameter informs BGPCK that YMODEM-G may be used.
The /M parameter informs BGPCK that Moby Turbo may be used.
-------------------------------------------------------------
FILES INCLUDED / USED
-------------------------------------------------------------
BGPCK.EXE - Main Program
BGPCK.DOC - This documentation file
BGPCK.CNF - Sample configuration file
BGPCK.HLP - Sample help file
DSZ *must* be in your GTPATH directory, where netmail requires
it to be.
BGPCK generates *.MSG files which are then compressed with
PKZIP into *.RDR files. BGRDR, or a compatible reader, reads
the *.MSG files after unpacking the *.MSG files. BGRDR makes
reply files, *.BAG, and zips them up as *.PCK files.
*All* files should reside in the GTPATH directory. The work
directory is used only for what it states, work, and should
be empty when not in use.
The BGPCK.CTL file is created and stored in the GTPATH
directory. This contains the users configuration information
and date of the last packet uploaded so duplicates don't
pop up.
A total of 255 message bases are supported.
BGPCK keeps a log file in the GTPATH directory. You can deal
with the log file in anyway you see fit; BGPCK.LOG.
A sample batch file that you may use to execute this door:
@echo off
rem ** Loading MailPack Door **
%1 gate%2
bgpck %2
%1 con
If you would be interested in writing your own reader or door
that will be compatible with mine, you are free to do so.
You will need to contact me to get the specs.
-------------------------------------------------------------
CARRIER MONITORING AND DOOR ROUTINES
-------------------------------------------------------------
You may logon as a local user and open the door. The CD
pin will not be checked. If you are logging on locally,
however, if you wish to upload replies, they must be in
the work directory, as DSZ.COM is not executed.
BGPCK does not support its own communcation routines. It
must use a "helping" program such as Gateway or Doorway to be
seen by the remote user.
If you use DOORWAY, be sure to include the /D parameter and
include the DWREDIR line in the BGPCK.CNF file. You *must*
be using DOORWAY 2.06 or above with BGPCK. Doorway 2.05 and
below WILL NOT WORK. (2.06 beta is currently available on
Marshall's system for registered users).
If you have your com port locked at a high baudrate and are
not using GT 15.50, estimated download times on files will
not be reliable. If you are using GT 15.50, BGPCK will send
DSZ the locked DTE baud rate and use the DCE user baud
rate for calculating download times.
If carrier is dropped during the door, the door will
"gracefully" return to GT and exit with an errorlevel of 1.
My carrier monitoring routine was a routine out of the ASYNC
TP communications library. It must be called several times
during the program. For interested programmers, here is the
coding that is necessary:
const c_portaddr : array[1..4] of word =
($03F8, $02F8, $03E8, $02E8);
var COMPORT : byte;
function dcdstat : boolean;
begin
dcdstat := port[c_portaddr[COMPORT]+6] and $80) > 0
end;
{ the +6 is a constant that is used on the 8250 uart }
{ COMPORT is a numerical value ranging from 1 to 4 }
-------------------------------------------------------------
OTHER INFORMATION
-------------------------------------------------------------
This program was written with Borland's Turbo Pascal 5.5 and
has been compressed with LZEXE 0.91.
If you have any suggestions or comments please address them
to me via netmail or any appropriate echomail conference, or
via a direct voice or BBS phone call.
There is no registration required. This program is free to
use, provided that you do not alter or reverse engineer the
program in anyway what so ever.
I may be contacted at AFSN 440/003 or RelayNet TRANQUIL.
Regards, AfsNet 440/003
B.J. Guillot (713) 893-9124